feat: IPv6 connectivity support in NGINX One APIs #1135
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
github-actions
bot
added
documentation
|
I have hereby read the F5 CLA and agree to its terms |
mjang
reviewed
Sep 17, 2025
content/solutions/r33-pre-release-guidance-for-automatic-upgrades.md
Outdated
Show resolved
Hide resolved
mjang
approved these changes
Sep 17, 2025
travisamartin
approved these changes
Sep 17, 2025
|
Moving back to draft -- we need to test for confirmation (working in an internal issue) |
|
Holding until test confirmation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Added the note about recently introduced IPv6 connectivity support for NGINX One APIs endpoints.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩